perf: benchmark table region key plans#74
Merged
Conversation
TypeThe0ry
marked this pull request as ready for review
July 16, 2026 07:50
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
region-keystime/allocation profile and label mappingScope
Measurement infrastructure only. No production source is changed. A later candidate may cache immutable region keys only after this harness is merged and can judge the exact base/candidate pair.
Validation
No Gradle, JMH, tests, server, or client workload was run locally. GitHub Actions is the sole compiler, formatter, contract verifier, benchmark smoke runner, and server-infrastructure validator.